Course: Tableau Training | Topic: Publishing Workbooks and Data Sources | Level: Beginner to Advanced
Explore the complete process of publishing Tableau workbooks and data sources to Tableau Server or Tableau Cloud so that teams can securely access, interact with, and reuse reports and analytical data.
Register for a Tableau Course Demo
Publishing in Tableau means uploading a workbook or data source from Tableau Desktop or another supported authoring environment to Tableau Server or Tableau Cloud. Once published, authorized users can access the content through a browser or supported Tableau applications without needing the original workbook file on their computers.
Publishing makes it easier for teams to share dashboards, centralize data connections, maintain consistent calculations, manage permissions, and distribute business insights.
A company's sales analyst creates a dashboard showing revenue, profit, sales representatives, and regional performance. Instead of sending a workbook file to every manager, the analyst publishes it to Tableau Cloud. Managers can sign in, open the dashboard, apply filters, and review the latest available information according to the data connection and refresh configuration.
A Tableau workbook is a file or published content item containing analytical work such as worksheets, dashboards, stories, formatting, calculations, and data connection definitions.
Workbooks created in Tableau Desktop are commonly saved as .twb or .twbx files.
| File type | Description | Typical use |
|---|---|---|
.twb |
Tableau workbook definition that stores visualization and connection information but does not normally package all underlying data. | Workbooks that refer to accessible data sources. |
.twbx |
Packaged workbook that can include supporting files, extracts, and other required local resources. | Sharing a workbook with relevant packaged resources. |
.tds |
Tableau data source definition containing connection and metadata information. | Saving a reusable data source definition. |
.tdsx |
Packaged Tableau data source that can include associated supporting files or extracts. | Sharing a data source and its packaged resources. |
Important: A packaged workbook does not automatically guarantee that every external database dependency, credential, or refresh process will work in another environment. Verify the connection and authentication requirements before sharing or publishing.
A Tableau data source defines how Tableau accesses and prepares data for analysis. It can include connection details, tables, relationships, joins, metadata, field names, calculations, and, where applicable, an extract.
Data can come from Excel, CSV files, relational databases, cloud databases, and other supported connectors.
A sales data source may contain fields such as Order Date, Region, Product Category, Sales, Profit, and Customer ID. Multiple analysts can use this published source to create different workbooks without independently rebuilding the same connection and data model.
| Feature | Publishing a workbook | Publishing a data source |
|---|---|---|
| Main purpose | Share completed analysis and visualizations. | Share reusable, centrally managed data. |
| Typical contents | Worksheets, dashboards, stories, calculations, and connection references. | Connection details, data model, metadata, and optional extract. |
| Primary audience | Dashboard viewers, analysts, and business users. | Analysts and creators who need a common data source. |
| Reusability | Users can interact with the published analytical content according to their permissions. | Multiple workbooks can connect to the same published source. |
| Data updates | Depend on the workbook's connection and extract configuration. | Changes to the published source can affect connected workbooks. |
| Common example | Monthly Sales Performance Dashboard. | Central Sales Data Source. |
Best practice: Publish a workbook when the main goal is to distribute a finished analysis. Publish a data source when multiple people or workbooks need a shared, managed data foundation. Some workflows use both.
Before publishing to Tableau Server or Tableau Cloud, verify that the workbook and its data are ready for other users.
Publishing capabilities depend on the site's configuration, license, role, project settings, and administrator-defined permissions. If the publishing option is unavailable, contact the Tableau administrator.
The following workflow describes publishing a workbook from Tableau Desktop to Tableau Server or Tableau Cloud.
Launch Tableau Desktop and open the workbook containing the worksheets, dashboards, or stories you want to share. Check that the workbook opens and its data connection works correctly.
Use the appropriate sign-in option for your organization. For Tableau Cloud, connect to your organization's Tableau Cloud site. For Tableau Server, use your organization's configured server address.
From the top menu, select Server > Publish Workbook. Depending on the Tableau version and authoring environment, menu wording or navigation may differ.
If the option is unavailable, make sure a worksheet or dashboard tab is active rather than the Data Source tab, and verify your publishing permissions.
Choose the project where the workbook should be stored. Projects help organize content by department, subject, team, or business function.
Examples include Sales Analytics, Finance Reports, Marketing Dashboards, and Human Resources Analytics.
Example workbook name: Monthly Sales Performance Dashboard.
Select which sheets should be included and whether users should navigate between views using sheet tabs, where these options are available. Review device layouts for dashboards that will be used on phones or tablets.
Hiding a worksheet is not a security measure. Users with appropriate download or editing capabilities may still be able to access hidden content. Use permissions and data-security controls for sensitive information.
Review the workbook's data sources. Depending on the source and deployment, you may be able to use a published data source, embed credentials, prompt users to authenticate, or configure other supported authentication options.
If the workbook uses an extract, verify that the published content can access the required data and that refreshes are configured appropriately.
Use the project's approved permission settings unless the workbook requires an authorized exception. Confirm who can view, interact with, download, edit, or republish the workbook.
Click Publish and wait for the upload and processing to complete. Tableau may open the published workbook in a browser after publishing.
Publishing a data source makes a reusable data connection available to authorized users so that they can create new workbooks or connect existing workbooks to the shared source.
Open Tableau Desktop and connect to the required file, database, or other supported data source. If the workbook contains multiple data sources, identify the one you want to publish.
Review tables, joins, relationships, field names, data types, calculations, filters, and data quality. Remove unnecessary fields where appropriate and confirm that the model returns correct results.
Choose Server > Publish Data Source. If several data sources are available, select the specific source from the submenu.
Sign in to Tableau Server or Tableau Cloud and select the destination project.
Use a descriptive name, a useful description, and relevant search tags.
Example: Corporate Sales Data Source.
Determine whether the source should use a live connection or an extract. Configure authentication according to organizational policy and the source's supported connection options.
Confirm who can connect to the data source, view it, use it in workbooks, or manage it. The permissions required depend on the task and site configuration.
Click Publish. Tableau uploads the data source and may update the current workbook to use the newly published source if that option is selected.
An embedded data source is defined within a workbook. A published data source is stored as a separate, reusable content item on Tableau Server or Tableau Cloud.
| Aspect | Embedded data source | Published data source |
|---|---|---|
| Location | Defined within the workbook. | Published separately to the Tableau site. |
| Reuse | Other workbooks may need their own connections or copied definitions. | Multiple authorized workbooks can use the same source. |
| Management | Connection settings are managed as part of the workbook workflow. | Source can be managed centrally by authorized users. |
| Consistency | Separate copies may develop different calculations or definitions. | A shared source can help standardize fields and business logic. |
| Maintenance | Updates may need to be applied to multiple workbooks. | Source changes may flow to connected workbooks, subject to compatibility and the change made. |
| Best use | Self-contained or specialized analysis. | Shared, governed data used by multiple reports. |
Example: If five departments need the same definition of Net Sales, a centrally maintained published data source can reduce the risk that each department calculates it differently.
Choosing a live connection or an extract is an important publishing decision because it affects data freshness, performance, infrastructure requirements, and refresh management.
A live connection queries the underlying data source when the visualization needs data. Results depend on the underlying system, query behavior, permissions, and caching.
An extract is a stored snapshot of data that Tableau can query without issuing every analysis query against the original source. Extracts can be refreshed according to the supported configuration.
| Factor | Live connection | Extract |
|---|---|---|
| Data freshness | Queries the underlying source; actual freshness depends on the source and caching. | Reflects data available at the last successful refresh. |
| Query workload | Can place query workload on the underlying database. | Queries the stored extract for analysis. |
| Refresh schedule | Typically not an extract-refresh process; source availability and freshness still matter. | May use scheduled full or incremental refreshes where supported. |
| Network needs | Requires a supported route to the underlying source. | Requires a route to the source when the extract is refreshed. |
| Typical use | Analytics requiring current source data. | Analytics that benefit from a stored, refreshable data snapshot. |
There is no universally best connection type. Choose according to freshness requirements, source performance, data volume, security, and operational constraints.
Publishing an extract does not automatically guarantee that it will remain current. A refresh process must be configured when ongoing updates are required.
Tableau Bridge is a component that enables Tableau Cloud to work with certain data sources that Tableau Cloud cannot access directly because they reside on a private network. Depending on the configuration, Bridge can support live queries or extract-refresh operations.
Important: Tableau Server and Tableau Cloud have different administration models and supported configuration options. Follow the procedures appropriate to your deployment.
Projects provide a structure for organizing workbooks and data sources. A good project structure helps users discover content and helps administrators manage access consistently.
Actual capabilities are controlled by site roles, project settings, content permissions, and administrative policies. Avoid granting broad permissions when a narrower level of access meets the business requirement.
Good naming and metadata help users discover the correct workbook or data source and understand whether it is appropriate for their analysis.
Monthly_Sales_Performance rather than Workbook_Final2.| Property | Example |
|---|---|
| Workbook name | Monthly Sales Performance Dashboard |
| Description | Tracks sales, profit, order volume, and regional performance by month. |
| Tags | Sales, Revenue, Profit, KPI, Monthly |
| Project | Sales Analytics |
| Data source | Corporate Sales Data Source |
| Intended audience | Sales managers and business analysts |
When a workbook changes, the owner may need to republish it to update the published version. Changes to a separately published data source are managed independently and can affect workbooks that use that source.
Warning: Renaming or removing fields, changing data types, modifying calculations, or altering relationships can break existing workbook views. Test significant data-source changes before rolling them out broadly.
A company wants its regional managers to view monthly sales, profit, product performance, and sales trends through a shared Tableau dashboard.
| Order ID | Region | Category | Sales | Profit |
|---|---|---|---|---|
| 1001 | West | Technology | 50000 | 12000 |
| 1002 | North | Furniture | 30000 | 5000 |
| 1003 | South | Office Supplies | 20000 | 4000 |
| 1004 | West | Furniture | 40000 | 8000 |
| 1005 | North | Technology | 60000 | 15000 |
Open Tableau Desktop and connect to the Excel or CSV file containing the sales data.
Check that the dashboard's sales and profit totals agree with the source data. Test the filters and confirm that aggregations are correct.
If other teams need to build their own reports using the same sales data, publish the data source to a suitable project and configure its connection and permissions.
Publish the completed sales dashboard to the appropriate project. Give it a clear name and description, and confirm the correct source is being used.
Ask an authorized regional manager to open the published dashboard, use its filters, and confirm that the expected data is visible.
If the dashboard uses an extract that must be updated regularly, configure a supported refresh schedule and verify its successful completion. If the source is behind a private network and published to Tableau Cloud, determine whether Tableau Bridge is required.
Regional managers can access the shared dashboard, while analysts can reuse the centrally published data source to develop additional reports under the organization's access and governance rules.
| Problem | Possible cause | Suggested solution |
|---|---|---|
| Publish Workbook is unavailable | Wrong tab is active, the user is not signed in, or publishing permissions are missing. | Activate a worksheet or dashboard, sign in, and verify permissions with the administrator. |
| Publish Data Source is unavailable | The wrong data source is selected or the user lacks required capabilities. | Select the intended data source and check the site role and project permissions. |
| Authentication error | Credentials are missing, expired, or not valid for the deployment. | Review the authentication method and credential settings with the data owner. |
| Workbook opens but data is unavailable | Underlying source is unreachable or the viewer lacks data access. | Check connection availability, credentials, permissions, and network access. |
| Extract refresh fails | Source connectivity, credentials, schema, or scheduling problem. | Review refresh history, validate the source, and correct the connection or schedule. |
| Private-network source cannot refresh in Tableau Cloud | Bridge or an appropriate supported connection configuration is missing. | Check whether Tableau Bridge is required and verify its configuration. |
| Dashboard shows unexpected totals | Incorrect aggregation, duplicate rows, changed source data, or a data-model issue. | Validate the source, relationships, joins, filters, and aggregation logic. |
| Some users cannot see a workbook | Project or content permissions do not grant access. | Review effective permissions and grant only the access required. |
| Fields are missing after an update | The source schema or published data source has changed. | Review field names and types, then repair dependent calculations and views. |
| Workbook performs slowly | Large data volume, expensive queries, excessive marks, or inefficient calculations. | Optimize the workbook and data model, and evaluate the connection strategy. |
| Users see an older extract | The latest refresh has not run or failed. | Check the last successful refresh and configure or repair the schedule. |
Tableau Server and Tableau Cloud support controlled sharing within an organization through their authentication and permission systems. Tableau Public is designed for public sharing, so published content may be accessible to anyone.
| Feature | Tableau Server / Tableau Cloud | Tableau Public |
|---|---|---|
| Primary purpose | Organizational collaboration and managed analytics. | Publicly accessible data visualization and portfolio sharing. |
| Access control | Supports configured authentication and permissions. | Content is intended for public access. |
| Confidential information | May be used with appropriate organizational controls and policies. | Do not publish confidential or sensitive data. |
| Administration | Managed according to the Server or Cloud deployment. | Public sharing service with different management capabilities. |
Answer: Publishing is the process of uploading a workbook or data source to Tableau Server or Tableau Cloud so authorized users can access, interact with, and reuse the content.
Answer: A workbook contains visualizations such as worksheets and dashboards. A data source defines the connection and data model used for analysis. A published data source can be reused across multiple workbooks.
Answer: Open the workbook, sign in to the destination, select Server > Publish Workbook, choose the project, configure workbook details and connection settings, review permissions, publish, and test the result.
Answer: Select the intended data source, choose Server > Publish Data Source, select the destination project, enter the source name and metadata, configure connection and authentication options, review permissions, and publish.
Answer: A separate published data source can provide a reusable and centrally managed data model. It helps teams share consistent fields, calculations, and connection settings.
Answer: A live connection queries the underlying source when needed. An extract stores a snapshot of data that can be refreshed according to a supported schedule.
Answer: Not necessarily. Ongoing freshness generally requires a supported refresh configuration, working credentials, and connectivity to the underlying source.
Answer: Tableau Bridge helps Tableau Cloud access certain data sources that are only reachable through a private network. Depending on the setup, it can support live connections or extract refreshes.
Answer: A project is a container used to organize published content such as workbooks and data sources. Projects also help administrators manage content access.
Answer: Check the connection configuration, authentication, credentials, network access, data-source permissions, and refresh status. For private-network sources on Tableau Cloud, verify whether Bridge is required.
Answer: Yes. Multiple authorized workbooks can connect to the same published data source, which can help standardize data definitions across reports.
Answer: Publishing may expose differences in permissions, credentials, connectivity, device layouts, and refresh behavior. Testing confirms that the published version works for its intended users.
Answer: No. Hidden worksheets are not a security boundary. Use appropriate permissions and data-security controls.
Answer: Tags help users search for and discover related workbooks and data sources.
Answer: Review downstream workbook dependencies, field names, calculations, data types, relationships, and refresh behavior. Test changes before deploying them to shared content.
Publishing workbooks and data sources is an essential Tableau skill for sharing dashboards, supporting collaboration, and maintaining consistent analytics. Workbooks distribute completed visualizations, while published data sources provide reusable connections and data models for other workbooks.
A reliable publishing workflow includes validating data, choosing the correct destination, configuring connections and authentication, setting permissions, publishing, testing the published content, and maintaining data freshness where required. Applying these practices helps teams deliver secure, consistent, and useful business intelligence.
Continue Learning: Explore Tableau Training | Register for a Tableau Course Demo
